Software Project Planning |
| A clear and precise project plan is the most important part of any project. The plan helps to identify the resources that the project will require. The most important resources are money and time. |
Requirement Meeting (Step 1) |
| The first step to start a software project is to have a meeting to discuss the details of the program. Most information systems have the intention to replace some system that is already in operation. In some cases, this system may be based on email, Microsoft Excel files, forms or other type of document. So, before organizing the meeting the client must work on a brief presentation describing their current system. It is a good idea to invite to the meeting the people who are directly involved in the operation of the current system. |
System Proposal (Step 2) |
| Usually, a week or two after the requirement meeting, it is a good idea to have another meeting. In this meeting the company offering the service will present a draft of the information system. This draft may be presented by creating the GUI of the system but without any programming. Instead, the screenshots of the GUI must be accompanied of a brief document explaining how the GUI elements behave. |
Feedback (Step 3) |
| After a couple of weeks after the system proposal meeting, another meeting to provide feedback from the client should be organized. Before this meeting is concluded, both parts should agree on drafting a legal contract to decide the dates, cost and other details. The contract should indicate if the code or just the program is being negotiated. The contract must indicate in detail the number of GUI and when they will be completed. |
The Contract (Step 4) |
| Before signing the contract, an informal meeting can be organized to review the details of the contract. The client should provide its final comments about the proposal. After the contract has been signed, no more changes to the proposal can be made. Any suggestions by the client must be incorporated to a next version list. |
Testing (Step 5) |
| Once the software has been tested by the quality assurance team (QA), it can be delivered to the client for testing. Usually, the client should have two weeks to test the software. The client cannot use the software for production. After these two weeks of testing, the client must present a document explaining the problems found. The client cannot request the incorporation of new functionability that was not agreed in the contract. |
Release (Step 6) |
| A couple of weeks can be used to correct any bugs in the software before the release of it. Once the software has been released, the contract may allow a period of two months to correct any further bugs in the software. Once the software has been released, the client cannot ask for any improvements that were not indicated in the original contract. Two months after the release of the software, the client has to pay for additional changes or errors in the software. |
Basic Hardware and Software requirements of an Information System |
Economic
For Bussiness
Económica
Para Negocios
|
